System and method of delivering data that provides service differentiation and monetization in mobile data networks

ABSTRACT

An exemplary system according to the present disclosure comprises a lower tier Radiolet™ that is in communication with a local switching office of a mobile data network, and an upper tier Radiolet™ that is in communication with the lower tier Radiolet™ and an Internet datacenter. In operation, the upper tier Radiolet™ receives data extracted from the Internet datacenter and distributes at least a portion of the received data to the lower tier Radiolet™. At the lower tier Radiolet™, the portion of received data is stored. The lower tier Radiolet™ then receives a data request (relating to a portion of received data) and in turn, transmits data from the portion of received data to a source of the data request. The lower tier Radiolet™ is located closer to the source of the data request than the Internet datacenter to improve application performance and efficiency of network as well as datacenter.

TECHNICAL FIELD

The present disclosure relates generally to wireless communications, andmore particularly to content distribution and application delivery overmobile wide area networks. The present disclosure also relates tosystems and methods for providing service differentiation and assuranceover a wireless network for mobile Internet sites and mobileapplications providers.

BACKGROUND

Methods to mobilize the Internet and deliver content are undergoingtransformative changes. On the data networking side, mobile data networkoperators are able to provide mobile broadband services. On theapplication delivery side, cloud computing promises to simplifyapplication roll outs and catalyze adoption across multiple verticals.However, inefficiencies in mobile content distribution and applicationdelivery is impacting the entire value chain. Fundamentally, the valuechain consists of a series of independent islands of technology andbusiness owners, whose intentions and beliefs are often misaligned,leading to a number of inefficiencies due to the application and networknot working in tandem. These inefficiencies include high mobilelatencies, and inefficient use of network resources as well asapplication datacenter resources. Inefficiencies can be caused by datapaths, where data requests from a network subscriber's device arereceived at a cell site, then sent to a local switching office, and thento a regional switching office en-route to a network peering pointbefore being routed to an Internet datacenter that serves theapplication to the subscriber. The pathway within the wireless networkis rooted on the need to provide multiple layers of mobility managementand the need to centralize subscriber and session management. Thepathway above the wireless network is due to network peeringrelationships, geographic distribution of such network peering points,and diversity of application datacenter locations above the network andcentralized resource pooling of computing by application providers.Within the wireless network, the regional and central switching officesmay not be local to the area where the subscriber is and hence, dataserved traverses several hundreds of miles before reaching thesubscriber, creating a number of areas of inefficiency. More generally,applications are largely unaware of the network and tend to treat thenetwork as a blackbox; conversely, networks are unaware of applicationneeds and tend to treat applications as a sequence of packets. Oneproblem of applications being unaware of the network, and networkcontours, is a network topology issue that contemporary over the topsolutions cannot address. Given the economics of mobile data, operatorsdo not find a compelling need to upgrade networks without contenteco-system participation. Conversely, application awareness is notcurrently possible or available because it involves well more than justpropagating a few parameters into the network. Network nodes typicallydeal with packets and methods to forward such packets, however, suchnetwork nodes are not suitable for dealing with applications. Thismismatch between packet based network forwarding and the technology toservice applications contributes to the current lack of applicationawareness within the network. In general, there is a lack of“end-to-end” intelligence between the two end points of an application,leading to significant over provisioning of resources within the mobileoperator network and the various application datacenters. Existingmobile data networks are not built for a specific application, whilethere are thousands of applications, and conversely applications are notbuilt for specific network types with network state information of agiven network changing every instant.

Current partial solutions to the foregoing require an upgrade to theexisting mobile data network and require mobile operators tore-architect their networks, which leads to significant increases incosts. However, even such upgrades and modifications are incapable ofcreating application awareness in the network or provide networkawareness to the application.

In connection with the foregoing, it is desirable to have systems andmethods that can reduce the number of hops between the end points of theapplication, by bringing mobile content and application servers andInternet cloud content closer to the subscriber, as well as creatingoptimized paths between the end points especially when the end pointsare both clients and are local to the area. It is also desirable tocreate optimal paths for traffic data from a local switching office,while preserving all layers of mobility and tiered deployments, andallowing applications and networks to work with each other without anymodifications to the network or application datacenters. Additionally,it is desirable to create a framework along this optimized path whereinthe network and application can work in tandem.

SUMMARY

The present disclosure relates to systems and methods of delivering datacomprising at least one upper tier Radiolet™ receiving data extractedfrom an Internet datacenter and distributing at least a portion of thereceived data to at least one lower tier Radiolet™. The at least onelower tier Radiolet™ stores the portion of the received data and, inresponse to a data request, transmits data from the portion of receiveddata to a source of the data request. Notably, the at least one lowertier Radiolet™ and the at least one upper tier Radiolet™ are locatedcloser to the source of the data request than the Internet datacenter,thereby reducing the number of processing points between the end pointsof the application session. Furthermore, the at least one lower tierRadiolet™ and the at least one upper tier Radiolet™ may be both networkand application aware, thereby allowing network information andapplication information to be dynamically applied at the same locationto further reduce inefficiencies between the end points of theapplication session.

BRIEF DESCRIPTION OF DRAWINGS

The foregoing summary and the following detailed description are betterunderstood when read in conjunction with the appended drawings.Exemplary embodiments are shown in the drawings, however, it isunderstood that the embodiments are not limited to the specific methodsand instrumentalities depicted herein. In the drawings:

FIG. 1 illustrates an exemplary mobile communications network.

FIG. 2 illustrates an exemplary mobile communications network accordingto an exemplary embodiment of the present disclosure.

FIG. 3 illustrates an exemplary network signaling data flow pathway andan exemplary traffic data flow pathway according to an exemplaryembodiment of the present disclosure.

FIG. 4 illustrates an exemplary distribution of end to end functionalityaccording to an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION

The following definitions and descriptions are provided and may beuseful to better understand the concepts described in this disclosure:

“Radiolet™” refers to any type of server or servers, including thoseconfigured for use in connection with mobile data networks such as, forexample, any application servers, communications servers, proxy serversor any other suitably configured servers. The server or servers maycomprise any type of computer software and computer hardware, andinclude one or more processors for executing computer-readableinstructions. In an exemplary embodiment, a Radiolet™ may refer to atemporary and partial instance of a cloud (e.g., the Internet), embodiedand provide via one or more servers located at a radio edge (e.g., outerlimits of radio processing functions within a mobile data network), thatis configured to be application aware and to provide one or moreapplication services.

“computer” or “computer hardware” refers to any electronic device ordevices, including those capable of being utilized in connection with amobile data system, such as, for example, any device capable ofreceiving, transmitting, processing and/or using data and information. Acomputer or computer hardware may comprise one or more of the following:a server, a processor, a microprocessor, a personal computer such as,for example, a laptop computer, a tablet, a palm PC, a desktop or aworkstation computer, a network server, a mainframe, an electronic wiredor wireless device such as, for example, a telephone, a cellulartelephone, a personal digital assistant or a smart phone, an interactivetelevision such as, for example, a television adapted to be connected tothe Internet or an electronic device adapted for use with a television,an electronic pager or any other computing and/or communication device,whether located in a single or across multiple locations.

“network” refers to any type of network or networks, including thosecapable of being utilized in connection with a mobile data system suchas, for example, any public and/or private networks, including, forinstance, the Internet, an intranet, an extranet, or any wired orwireless network(s) or combinations thereof.

“data” refers to any type of facts, figures, statistics, details,images, multi-media content, quantities, characters, symbols or anyother type of information and/or communication, including those capableof being utilized in connection with a mobile data network such as, forexample, any Internet content data or Internet application data, thatmay be received, processed, stored and/or transmitted by a computer inthe form of electrical signals and recorded on magnetic, optical, and/ormechanical recording media.

“datacenter” refers to one or more networked computer servers configuredfor receiving, processing, storing and distributing large amounts ofdata. For purposes of the present disclosure, datacenters may also beconfigured to operate within mobile data networks such as, for example,an Internet cloud-based datacenter.

“application” refers to a collection of one or more computer-readableinstructions that when executed, carry out one or more specificoperations. In the context of the present disclosure, an application maybe embodied as software executing on one or more computers andconfigured to perform operations for use in connection with mobile datanetworks, although the present disclosure is not limited thereto. Forpurposes of the present disclosure, an application may be configured foruse in conjunction with any operating system platform, such as, forexample (and without limitation), Windows®, Android®, and Apple®.

In the context of wireless Internet communications, mobile applicationperformance can be significantly inferior as compared to wired Internetcommunications. For instance, the latencies may be extremely highcompared to wired Internet communications. The higher mobile latenciescan be due, at least in part, to the “Mobile Middle Mile™” problem.Moreover, the Mobile Middle Mile™, combined with the lack of end-to-endintelligence, also leads to a number of inefficiencies in resourceutilization in the network as well as datacenter. This problem can occurwhen a subscriber accesses a mobile site or application through a mobiledata network. Data requests from the subscriber's device can be receivedat a cell site, and then sent to a local switching office, followingwhich data packets are tunneled to a regional switching office, followedby tunneling to a central switching officer, before being routed to anInternet datacenter via a network peering point. The data packetstraverse multiple switching offices before being routed to the Internetin order to provide multiple layers of mobility management andcentralization of subscriber and Internet session management. Oftentimes, the data requests will pertain to data that is typically locallyavailable at a datacenter close to the local switching office or pertainto applications between two end points that are in geographic proximityto each other. However, the regional and central switching offices, aswell as peering points and application datacenters, may not be local tothe area where the subscriber is and hence data packets may have totraverse several hundreds of miles before reaching the subscriber. Thisdata traversal across multiple switching locations can create highlatency. The data path from the local switching office to the Internetdata center that serves the subscriber may be referred to as the “MobileMiddle Mile™” problem.

As will be evident from the following description, the presentdisclosure provides means for addressing the Mobile Middle Mile™ problemby reducing round trip time (RTT) for traffic data packets coupled withimproved application performance through propagation of network andapplication intelligence in the path while simultaneously improving theefficiency of mobile broadband connections by bringing Internet cloud orcontent closer to subscribers. The present disclosure can also achieveimprovement in radio efficiency by improving the number of pages,videos, and applications transmitted per Megahertz of spectrum,improvement in transport efficiency by reducing the number of trafficpackets that traverse the transport network, improvement in core networkefficiency by reducing the number of traffic packets that traverse thecore network, and improvement in datacenter efficiency by reducing thenumber of content and/or application traffic sessions that are hosted inthe datacenter.

The present disclosure also provides means for the retention ofcentralized control within a mobile data network of functions related to(without limitation): subscriber management, session management,mobility management, policy management, peering, and other specializedfunctions such as intercept, the retention of centralized control withina cloud datacenter related to: application layer authentication,application databases, content ingestion and storage, applicationpeering, and other specialized functions such as usage metrics andreporting, and the decentralization of content distribution, applicationdata, application hosting, and delivery of such packets from a locationin the network much closer to the subscriber. Referring briefly to FIG.4, an exemplary (non-limiting) listing of such functions, together withvarious locations/apparatus across which such functions may bedistributed and performed, is shown.

The present disclosure also provides means for mobility at theapplication or content layer, when content and application data areserved from or hosted at a location in the network much closer to thesubscriber, by which the application service point is migrated to yetanother closer point in the network as the mobile subscriber migratesfrom cell tower to another or when network control migrates from oneswitching office to another midway through an application session.

The present disclosure also provides means for simultaneously improvingthe efficiency of every segment of an existing mobile data networkwithout having to upgrade said existing network or cloud/applicationdatacenters within said network. In addition, the present disclosureprovides means for improving efficiency of mobile operator networks aswell as Internet cloud datacenters by reducing the amount of trafficpackets that traverse through an existing mobile data network, allowingdata packets to traverse the existing mobile data network faster. Also,the present disclosure can combine an existing mobile data network witha network of software and Radiolets™ that have an independent managementsystem and network operations center for the software and Radiolets™,thereby eliminating the need for an upgrade to the existing mobile datanetwork. The present disclosure can be operator friendly and includessoftware and Radiolets™ combined with an existing mobile data networkthat allows the operator to retain subscriber and session managementthrough a core network of the existing network, while traffic requestsare served to the Radiolets™ from the local switching location.

In addition, the present disclosure provides means for identification oftraffic flow data from signaling flow data, and serving content andapplication data from the local switching office. The signaling flowdata are permitted to pass through an existing mobile data network thatinclude servers and specialized hardware for handling network subscribermanagement, network session management, and network mobility management,without any changes. Similarly, application layer signaling flow datamay be permitted to go to existing application data centers for handlingapplication layer session set up and application provider managementfunctions. The traffic flow data may be directed to pass through anothermobile data network or more generally another Internet Protocol (IP)based data network. The present disclosure can also provide means fordistribution, storage, and delivery of content, as well as hosting ofapplications from the local switching office, in the other mobile datanetwork. As indicated above, FIG. 4 provides a summary of various(exemplary) functions and the locations/apparatus across which suchfunctions may be distributed and performed. Notably, thesignaling/management entities may be separated from traffic functionsand the traffic functions may be moved closer to the user withoutrequiring upgrades to existing network or datacenters.

The present disclosure can also provide for a software based adaptiveoverlay solution, which operates on standard servers, across a highlydistributed network that does not require any upgrades to existingoperator networks or to the datacenters, including Internet cloud baseddeployments, of content and mobile applications (“apps”) providers. Thissoftware based adaptive overlay solution can provide means forseparating the control planes of mobile routers or switches from thedata planes of the routers or switches of a mobile data network as wellas application servers or application switches of a datacenter. Thecontrol planes can comprise signaling data transactions and the dataplanes can comprise traffic data transactions. An Internet datacenter,for example, a cloud-based datacenter, may be brought to the data planesand the combined data plane/internet cloud may be brought close to amobile subscriber. The combined data plane/internet cloud can distributemobile networking and mobile computing data to a location close to thesubscriber. The network control plane can be used for managementfunctions and can be preserved in a centralized manner in the existingnetwork elements of the mobile data network and the application controland management functions can be preserved in a centralized manner in theexisting application servers of the application cloud datacenters.Moreover, such preservation can be accomplished in a transparent mannerwithout any upgrades to existing mobile data network or applicationdatacenter. For example, any of the exemplary functions listed in FIG. 4may be distributed and performed across existing network elements, whileat the same time preserving application control and management functionsin existing application services and cloud datacenters.

Still further, the present disclosure provides means for intelligentcross layer resource management and flow control methods simultaneouslyapplied to network packet flows and content delivery and applicationsessions, which can lead to dramatic improvements in operatingefficiency of the spectrum.

Still further, the present disclosure can provide means for increasingdata transaction volume across a mobile data network and reducing churnrate, where churn rate is the percentage of subscribers in a given timeframe that cease to use the content or application provider's services,which can be beneficial to a mobile content or application provider. Thepresent disclosure can provide means for increasing the amount ofcontent and application transactions per megahertz (MHz) of cellularfrequency at a reduced cost, which can be beneficial to a mobileoperator. The present disclosure can also provide means for improvingquality of experience (QoE) for mobile services by reducing mobilelatency, which can be beneficial to a subscriber and an enterpriseapplication user.

Still further, the present disclosure can provide means for increasingthe richness of applications delivered from application datacenters andincreasing application adoption with corresponding application churnrate as well as customer acquisition costs. The present disclosure canprovide means for improving the number of application sessions supportedacross a given a datacenter footprint thereby reducing the cost ofapplication delivery. The present disclosure can also provide means forhigher definition quality of experience (hi-def QoE) for mobileapplications which can be beneficial to subscribers and enterpriseapplication users.

In an exemplary embodiment, the present disclosure can include thefollowing two tier distributed architecture: a lower tier network ofservers (e.g., lower tier Radiolet(s)™) that interface with an operatornetwork and an upper tier network of servers (e.g., upper tierRadiolet(s)™) that interface with a content and application providereco-system, including, for example, a publisher, advertising network, orenterprise datacenter, or over the top communications applicationprovider datacenter. One or more of the Radiolet(s)™ may represent atemporary and partial instance of a cloud (e.g., a cloudlet such as theInternet), embodied and provide via one or more servers located at aradio edge (e.g., outer limits of a mobile data network), that providesapplication aware and application service(s), and that comprisessoftware capsules such as, for example, application programminginterfaces (APIs). This type of radiolet instance may be referred to asRadio Edge Cloudlet™. One or more lower tier Radiolet(s)™ can beconnected to one or more upper tier Radiolet(s)™ using a high speedmanaged link, while upper tier Radiolet(s)™ may be logically connectedto each other through the Internet. Adequate security and redundancy canbe provisioned between the lower tier Radiolet(s)™ and the upper tierRadiolet(s)™ as required or desired.

The lower tier Radiolet(s)™ can comprise one or more servers and storagedevices, and can be located at a local switching office of a mobile datanetwork operator. The location of the lower tier Radiolet™ may depend ontransportation costs, for example (and/or other factors). A plurality ofcell sites can also be aggregated at the local switching office. In oneembodiment, an optimal location for the lower tier Radiolet™ can be alocation that is relatively close to subscribers, but yet does notrequire significant capital expenditure. The lower tier Radiolet(s)™ canbe physically connected to a layer 2 or layer 3 switch, where the layer2 switch provides connectivity from the local switching office to aregional switching office, and the layer 3 switch provides connectivityfrom the regional switching office to a central switching office, or arouter that is part of the overall network in a local switching officeof a mobile data network. In one exemplary embodiment of thisdisclosure, during operation, the lower tier Radiolet(s)™ may beconfigured to provide one or more of the following functions: passivelymonitor control signaling messages (for example, A11 messages in an HighRata Packet Data (HRPD) standards based mobile data network) and extractrelevant parameters while processing of and responding to saidcontrolling signaling messages (for example A11 messages in an HRPDstandards based mobile data network) is handled by network elements inthe packet core (for example a Packet Data Service Node (PDSN) in andHRPD standards based mobile data network); encapsulate and tunnel datatraffic packets (for example, A10 packets in an HRPD standards basedmobile data network) for bearer packets; potentially communicate withthe upper tier Radiolet(s)™ to dynamically fetch the content data, whichcan be based on the business relationship with over-the-top (OTT)content and application partners, where the OTT partners can be anyprovider of mobile content or application data; be a serving point forthe subscriber Internet protocol (IP) sessions, which means that asubscriber IP session is not extended up to the upper tier Radiolet(s)™;process dynamic content, support content caching and storage, which canbe used for accelerated and efficient content delivery; communicate withthe operator proxy Radiolet(s)™ to send and receive messages to policyand charging rules function (e.g., PCRF) servers, real time mediationdevice (RTMD) and authentication, authorization, and accounting (e.g.,AAA) servers; work with the operator proxy Radiolet(s)™ to enablecontent layer mobility during network mobility events (for example,layer two handoffs or inter-packet control function (PCF) handoff in anHRPD standards based mobile network); network and application layerquality of service (QoS) enablement; and work with operator owned lawfulintercept network elements.

In another exemplary embodiment of this disclosure, the said tunnelingand delivery of data traffic packets (for example, A10 messages in anHRPD standards based mobile data network) is achieved without anyextraction of parameters contained in control signaling messages (forexample, A11 messages in an HRPD standards based mobile data network)but instead through a combination of an automated learning method thatobserves packet flows between the packet core and RAN as well interfaceswith existing management nodes and billing as well as accounting systemsin the operator network.

The upper tier Radiolet(s)™ can comprise one or more servers and storagedevices located in a hosting datacenter(s) external to operatornetworks. The upper tier Radiolet(s)™ can serve multiple lower tierRadiolets™ across multiple operator networks in a given geographic area.The upper tier Radiolet(s)™ can be physically connected to a layer 2 orlayer 3 switch or a router that is part of the overall network in aprivate or public cloud datacenter. The upper tier Radiolet(s)™ cancomprise back to back (B2B) user agents and open application programminginterfaces (API) that can interface with multiple application deliverydatacenters and third party software products. In one embodiment, theupper tier Radiolet(s)™ may not be co-located or located in the packetcore (for example, next to a packet data serving node (PDSN) of an HRPDstandards based mobile network) or any point of present (PoP) of amobile data network, but rather located close to the user outside themobile data network with a view towards enabling functionality that istypically available at a private application data center or publicInternet cloud datacenters. In one embodiment of the operation, theupper tier Radiolet(s)™ can provide one or more of the followingfunctions (but not limited to): support a mobile web services enginecoupled with dynamic on demand virtualization to support multiplesessions across multiple content properties; distribute contentdynamically to the lower Radiolet(s)™; and serve multiple operatornetworks. Also, in an exemplary embodiment, any upper tier Radiolet(s)™can communicate with multiple lower tier Radiolet(s)™ within a givengeographic area, through a high speed managed network, which will allowfor leveraging of statistical multiplexing gains, without any impact oncontent distribution, application delivery, and corresponding serviceassurance.

In an exemplary embodiment, a system according to the present disclosurecan also include a lower tier network of proxy servers (herein referredto as “operator proxy Radiolet(s)™”) and an upper tier network of proxyservers (herein referred to as “over the top proxy Radiolet(s)™”). Theoperator proxy Radiolet(s)™ can be configured to support interfaces tobilling and policy enforcement in the operator network. The operatorproxy Radiolet(s)™ can be configured to facilitate proxying of messagesfrom a plurality of lower tier Radiolet(s)™ towards an accounting server(for example, a AAA server), and towards a billing server (for example,towards a diameter based billing system), and towards a policy server (aPCRF server, for example, in HRPD standards based systems). The operatorproxy Radiolet(s)™ can facilitate content layer mobility duringinter-PCF handoff. The operator proxy Radiolet(s)™ can be locatedrelatively close to the packet core (for example close to a PDSN in andHRPD based mobile data network). The over the top proxy Radiolet(s)™ canbe located in a large geographic area and can support interfaces tometering and application policies across multiple content andapplication datacenters, or customized to support specific largeapplication provider in a private datacenter of the said applicationprovider. The location of the both operator and over the top proxyRadiolets™ may depend on transportation costs, operations costs, andother costs for example (and/or other factors including businessagreements and policies).

The present disclosure can provide means for supporting content andapplication layer mobility which exploits two tier network architectureand can include a distributed network management system that provideshigh availability managed services with or without any tight integrationto operator network management systems or content eco-system datacenternetwork management systems. The present disclosure can also providemeans for interfacing to content or application eco-system partnerdatacenters, as well as mobile data network operator partner networksthat can be customized based on various requirements. The presentdisclosure can also provide means for supporting specialized servicessuch as, for example, mobile streaming, peer to peer communicationsservices, and real time TV services to mobile subscribers.

In another exemplary embodiment, data is fetched from variousparticipating Internet sites and/or enterprises, and made available toone or more upper tier Radiolet™ locations. The data can include, but isnot limited to, content, media feeds, and application data. One or moreof the upper tier Radiolet(s)™ obtains the data, following which thedata can be replicated across multiple other upper tier Radiolet(s)™ inmultiple locations. The choice of other upper tier Radiolet(s)™ thatobtain data from the upper tier Radiolet(s)™ may depend on variousstatic and dynamic rules. Exemplary static rules may include contenttypes and policies provided in advance by content partners, wherecontent partners can be any providers of mobile content or data, anddynamic rules may be created periodically based on outputs ofintelligent content management algorithms. The data may then bereplicated in one or more lower tier Radiolet(s)™. The lower tierRadiolet(s)™ can fetch the data from the upper tier Radiolet(s)™ or theupper tier Radiolet(s)™ can distribute the data to the lower tierRadiolet(s)™. Parameters for deciding which pieces of data are stored ina given lower tier Radiolet™ may be based on the frequency of requestsfor the same piece of data (for example, the popularity of data),networking, datacenter, and business policies, or any other desiredparameters.

When a subscriber mobile device requests for traffic data, this requestmay be delivered to the lower tier Radiolet(s)™ in the network that isclosest to the subscriber. In one exemplary embodiment of thisdisclosure, the closest lower tier Radiolet(s)™ to the subscriber can belocated at the local switching office where the traffic request from thesubscriber is received. Directing the traffic request to the closestlower tier Radiolet(s)™ may include identifying and separating trafficpackets from network signaling and application layer signaling packets(from the subscriber mobile device). In one embodiment, suchidentification and separation can be implemented in a switch thatmanages and communicates across all lower tier Radiolets™. Then, allnetwork signaling data may be sent directly to the mobile packet corenetwork, where the core network can comprise various servers providingvarious particular functions such as, for example (and withoutlimitation), policy and charging rules function (e.g., PCRF) servers,real time mediation device (e.g., RTMD) and authentication,authorization, and accounting (e.g., AAA) servers, and packet dataserving node (PDSN) servers, or other network elements known in the art.Similarly, application signaling packets may be sent to appropriateapplication provider data centers. Next, all data packets that are notsignaling may be declared as traffic packets, and directed to the lowertier Radiolet(s)™. The lower tier Radiolet(s)™ may then create atemporary instance of the content/media/application session and servicethe request in a manner similar to an existing content/media/applicationserver in a cloud datacenter. In one embodiment, the saidcontent/media/application server may create a flow control protocolsession such as, for example, a transmission control protocol (TCP)session, with the subscriber mobile device using existing Internetprotocols, and deliver traffic data as a flow control protocol, or forexample, a TCP, datagram. Following completion of thecontent/media/application session, additional sessions from the same ordifferent subscriber mobile device(s) may then be processed using thesame procedures. In an embodiment, a wireless link is shared acrossmultiple users, and multiple cell towers or wireless access devices areaggregated at a given local switching office, and accordingly, a givenlower tier Radiolet™ server can process and serve multiple user requestsas well as re-use the same hardware and software to support multipleusers across time.

The present disclosure can achieve efficiency improvements in thenetwork through one or more of the following: fundamentally, fetching,storing, and delivering data from the closest lower tier Radiolet(s)™reduces the latency of the content/media/application session and canallow more subscriber sessions to be hosted on the same network;completing a session in a shorter amount of time also allows for a givensubscriber mobile device to stop sending physical layer control messages(e.g., pilot beams and channel quality information), which can allow thenetwork to admit additional subscribers who may be able to makeadditional traffic data requests; and through a combination of resourcemanagement and flow control methods, additional and significant gains inoperating efficiencies in the spectral efficiency can be achieved whichcan allow for faster flow control protocol sessions. Furthermore,following the completion of a data content or application session, thepresent disclosure can allow for additional sessions from the same ordifferent subscriber mobile devices using the same methods.

In an embodiment, the present disclosure can additionally improveoverall efficiency and dramatically improve user Quality of Experience(QoE) through software APIs that provide network awareness to theapplication thereby allowing applications to adapt to the network typeand network state changes in real time as well as application awarenessto the network to intelligently allocate and manage resources in theradio access network.

In one embodiment, the present disclosure can include the followingfeatures (without limitation), applicable to a content eco-systemsubscriber base: the lower tier Radiolet(s)™ may directly providestorage and caching for static content/pages; dynamic mobile contentacceleration may be provided through a hybrid caching/storage and mobileweb services solution; the functionality for dynamic site accelerationmay be split between both the upper tier and lower tier Radiolet(s)™;application delivery frameworks may be hosted at a lower tier Radiolet™or at an upper tier Radiolet™, while application data that is frequentlyused may readily be available in an upper tier Radiolet™, whereas seldomused data may be fetched from an application partner's origindatacenter, where the application partner can be any provider of mobilesoftware application content or services; and both the lower tier andupper tier Radiolets™ can be configured to create temporary virtualcomputing instances to support application hosting based on applicationlogic provided by an application provider applied to various applicationdelivery frameworks.

Both the upper tier Radiolet(s)™ and lower tier Radiolet(s)™ may beconfigured to support any type of software application, and softwareapplication roll out (e.g., its introduction to the general public), maydepend on business strategy and product management input from contenteco-system subscribers.

The present disclosure can provide various “value added services”packaged around application programming interface (API) information (inthe form of metadata) that will abet monetization. The presentdisclosure can provide the value added services to subscribers, butobtain them from operators as well as other third party vendors, whileproviding necessary information to generate these monetization API's,essentially acting as a “super market shelf” for the value addedservices.

The present disclosure provides for communication between any upper tierRadiolet(s)™ and multiple lower tier Radiolet(s)™ within a geographicarea, which can allow the leveraging of statistical multiplexing gains,at no additional power or additional computing or additional bandwidth.

The present disclosure also provides various value added services can beprovided to the subscribers through the mobile data network that, fromthe content eco-system subscriber perspective, allows the accelerationof roll out of new services and leveraging of market opportunitiesearlier than currently possible.

The present disclosure also provides means for faster Internet webpageload times, and increased subscriber traffic on Internet webpages whichcan result in more and potentially richer media advertisements beingserved on the webpages, and can benefit advertisement supportedpublisher sites. In addition, the present disclosure provides means forfaster and potentially richer delivery of advertisements on Internetwebpages and can benefit advertisement networks and advertisers. Stillfurther, the present disclosure provides means for reduction insubscriber transaction latency and faster speeds for advertisements andrecommendations, and can benefit mobile commerce websites. Faster mobileapplication response times which can benefit enterprise networks arealso a direct result of the systems and methods described herein.

The present disclosure also enables the roll out of new rich media basedservices such as video based mobile commerce services, video basedbranchless banking and teller services, for example, without waiting formobile operator networks to increase capacity in their networks orenterprises to increase their datacenter capacities.

In one embodiment, the present disclosure may provide the followingfeatures (without limitation), applicable to mobile data networkoperators: the lower tier Radiolet(s)™ can interface with any mobilebroadband access network, including any 2G or 3G or 4G or futureGeneration network; and a 3G (or comparable) network can comprise aradio network controller (RNC) that terminates layer 2 protocols at alocal switching office followed by a visited mobile gateway (e.g., apacket data service node (PDSN) or serving general packet radio service(GPRS) support node (SGSN)) at a regional switching office and finally ahome gateway (e.g., high-availability HA or gateway GPRS support node(GGSN)) at a central switching office, which allows the operator toprovide inter cell site mobility by anchoring at the RNC, inter localswitching office mobility by anchoring at the visited gateway, and interregional switching office mobility by anchoring at the home gateway. Forexample, a 4G (or comparable) network may comprise local switchingoffices that contain an S1 aggregation device and interface as well asto a Mobility Management Entity (MME), regional switching offices thatcontain a visited gateway (e.g., serving gateway S-GW), and centralswitching offices that contain a home gateway (packet data node gatewayP-GW). In all such deployments, the lower tier Radiolet™ can beinterfaced in an adaptive overlay fashion at a local switching office(for example) or any other point in the radio access network closer tothe user.

In another embodiment, the present disclosure provides content andapplication services as well as network efficiency services for operatormanaged outdoor and indoor WiFi networks that are centrally connected toa common packet core.

In another embodiment, the present disclosure provides the features tosimultaneously service subscriber application and content requestsacross multiple radio access technologies supported the same mobile datanetwork operator from the same lower tier Radiolet™.

Traffic data packets between the core network, where the core networkcan comprise various servers providing various functions, for example,policy and charging rules function (e.g., PCRF) servers, real timemediation device (e.g., RTMD) and authentication, authorization, andaccounting (e.g., AAA) servers, and packet data serving node (e.g.,PDSN) servers, and the Radio Access Network (RAN), including networkelements in the local switching office, can be tunneled using differenttypes of IP in IP tunneling, where the type differences may be due todifferent standards. Similarly, packets between the lower tierRadiolet(s)™ and the RAN may also be tunneled with identical markings.This allows the existing network elements to not go through an upgradeto process packets from the servers. In an embodiment, the lower tierRadiolet(s)™ are not exposed to the RAN or network elements in thepacket core by reconfiguring the appropriate Ethernet interface or layer2 or layer 3 switch where the Radiolet(s)™ are located.

Intelligent algorithms can be provided to improve the efficiency of theRAN by increasing the number of pages/sessions that are delivered orcompleted in a unit of time over a given unit of spectrum. This can beachieved through a set of cross layer optimizations that can be appliedto existing flow control algorithms that are typically part of TCP, andtreating flow control as an outer loop control mechanism adapted to workwith existing mac layer scheduling algorithms. In an embodiment, thepresent disclosure does not require any modifications to the mac layerscheduling algorithms.

A coordinated exchange between source and target serving nodes ofcontent information as well as TCP parameters, referred to as “contentlayer mobility,” can be provided for session continuity. This addressesthe issue of a subscriber migrating from one content or application dataserving Radiolet™ or node to another node during a content orapplication session.

The present disclosure can operate above the RAN which can provide foran architecture and deployment agnostic solution, which means that thepresent disclosure is not constrained by the type of data networkdeployment of mobile operators (e.g., macro, micro, pico and femtocellular deployments).

Information delivered from an operator proxy Radiolet(s)™ to lower tierRadiolets™, can be used to enforce all operator policies applicable totraffic handled typically handled by core networking elements.

The present disclosure does not require existing mobile communicationsnetwork elements in an existing operator network to undergo an upgrade.Any software downtime from the existing mobile data network on the lowertier Radiolet(s)™ or upper tier Radiolet(s)™ of the present disclosuredo not negatively impact the existing operator network, and normal dataflows through the existing mobile communications network will continueto be supported by the present disclosure.

The lower tier Radiolet(s)™ may not be “reachable” from the Internet,except from the corresponding upper tier Radiolet(s)™. As a result,introduction of the lower tier Radiolet(s)™ into existing mobile datanetworks will not compromise the networks' security or the security ofthe networks' elements in the networks' local switching office or thelocation(s) where a lower tier Radiolet™ is deployed.

The upper tier Radiolet(s)™ may not be “reachable” from the publicInternet, except through managed connections from an over-the-top proxyRadiolet™ or from managed secure network connections from specific overthe top datacenters. As a result, introduction of the upper tierRadiolet(s)™ between the subscriber and the over the top datacenter willnot compromise the datacenters' security or the security of datacenterservers or cloud datacenter.

Lawful intercept functions (e.g., obtaining mobile communicationsnetwork data pursuant to lawful authority for purposes of analysis orevidence) can continue to be performed. In one embodiment of thisdisclosure, once a target subscriber is “identified” for a lawfulintercept purpose, the subscriber's data flows may be tagged and can beserved through the existing packet core network of the mobilecommunications network.

Once implemented, the systems and methods described herein reducecapital expenditures and operational expenditures in the mobile datanetwork and monetization of the efficiency improvements by sharingexisting mobile transport network with other mobile operators. Thesesystems and methods also improve the utilization of mobile frequencyspectrum by increasing the number of webpages/app sessions andsubscriber sessions per megahertz of spectrum. In addition, the systemsand methods of the present disclosure reduce RAN costs by increasingdata traffic flow per cell site of a mobile data network, and add “valueadded services” including (without limitation) location based serviceenablers, reduction in transaction time for mobile commerce and othertransaction services, improved performance for near real-time services(e.g., stock quotes, broking solutions), and to offer the value addedservices to mobile enterprise customers as well as subscribers.Implementation of the systems and methods described herein also providemeans for accelerating and monetizing Wifi content and mobile broadbandcontent using a single mobile data network that accommodates both Wifiand mobile broadband technologies.

Optionally, a system according to the present disclosure may beconfigured to generate data records and can feed into an existingbilling support system of a mobile data network. In addition to standardrecords, given the metering support provided to the content eco-system,such a system can provide fine grained micro usage records that canpotentially be used by operator analytics engines, for example.

Turning now to FIG. 1, an exemplary mobile communications network 100 isshown. The exemplary mobile communications network can comprise any typeof mobile communications network, including (without limitation) a HighRate Packet Data (HRPD) network, a High Speed Packet Access (HSPA)network, or a Long-Term Evolution (LTE) network, for example.

The exemplary network 100 includes a base station controller and packetcontrol function (BSC/PCF) network element or servers 101 that can belocated at a local switching office (not shown). Notably, it should beunderstood that exemplary network element 101 can be a Radio NetworkController (RNC) of a HSPA based network or an S1 aggregator element ofan LTE based network, for example. The local switching office can be incommunication with one or more cell sites (not shown) where the cellsites receive data requests from one or more subscriber mobile devices(not shown). The subscriber mobile device can be any device that can beutilized in a mobile data network including, for example, cell phones,personal digital assistant (PDA) devices, laptops, smart phones,tablets, etc. In operation, the base station controller and packetcontrol function (BSC/PCF) server 101 (or an RNC of an HSPA network)sends and/or receives data or information to a mobile data networkinterface 105 where the mobile interface 105 may include an AAA server102, a policy server 103 and a prepaid server 104. The BSC/PCF server101 represents a layer 2 termination point in a HRPD network. In a HSPAnetwork, this element may be called a Radio Network Controlled (RNC),and in a LTE network, this element may be called an S-1 interfaceaggregator.

The BSC/PCF server of an HRPD network 101 (or its equivalent in HSPA orLTE network) is in communication with the mobile data network interface105 via a L2 switch or L3 switch or policy based router (PBR) switch, ora general purpose router 111 and a managed IP network 121. The BSC/PCFserver 101 is also in communication with the mobile data networkinterface 105 via a L2 switch or L3 switch or PBR switch or generalpurpose router 112 and managed IP networks 122 and 123. In an HRPDnetwork, the BSC/PCF server 101 is in communication with a PDSN server106 via a L2 switch or L3 switch or PBR switch or general purpose router111, a managed IP network 122 and L2 switch or L3 switch or PBR switchor router 112. In one embodiment of this disclosure, the PDSN server 106may communicate with an Internet datacenter 108 through a router 113over an Internet connection 107 (or any other wired or wirelesscommunications link). The PDSN server 106 can provide managementfunctions (e.g., IP address allocation, content filtering, and sessionrecovery), data functions (e.g., interface for traffic data messages,policing of traffic data messages, and deep data packet inspection) andcontrol functions (e.g., interface for signaling data messages, routingof data, and acting as virtual local area network (VLAN)).

In one embodiment of this disclosure, during normal operation, theBSC/PCF server 101 sends data request(s) received from a subscribermobile device to the PDSN server 106. The PDSN server 106 in turn sendsthe data request(s) to the Internet datacenter 108 though the Internetconnection 107 (or any other wired or wireless communications link). TheInternet datacenter 108, in response to the data request(s), sendsrequested data to the PDSN server 106 via the Internet connection 107and through router 113. The PDSN server 106 then sends the requesteddata to the BSC/PCF server 101 using one or more switches/routers (e.g.,L2 switch, L3 switch, or PBR switch, or router 111, 112) over one ormore managed IP networks 122. Once the requested data is received at theBSC/PCF server 101, it may be sent to the subscriber mobile device (thatmade the initial data request) via the cell site (not shown).

Turning now to FIG. 2, an exemplary mobile communications network 200according to an exemplary embodiment of the present disclosure is shown.The exemplary mobile communications network 200 may comprise any type ofmobile communications network including (without limitation) a High RatePacket Data (HRPD) network, a High Speed Packet Access (HSPA) network,or a Long-Term Evolution (LTE) network, or operator owned WiFi accessnetwork managed through a common centralized packet core network, forexample.

Included in this exemplary network 200 is an upper tier Radiolet™ 233comprising at least one processor executing computer-readableinstructions that receives data extracted from for example an Internetdatacenter 209 (or a private cloud datacenter or privately ownedapplication datacenter or any other type of datacenter) through anInternet connection 235 (or via any other wired or wirelesscommunications link). Notably, although the exemplary network 200depicts a single upper tier Radiolet™ 233, it should be understood thata system according to the present disclosure may include any number ofupper tier Radiolets™.

The upper tier Radiolet™ 233 is located at or proximal to, for example,an Internet datacenter 209, which in this exemplary network 200 includesa content server 236, and the content server 236 is in directcommunication with Internet datacenter 209 via Internet connection 235(or any other wired or wireless communications link). The content server236 may obtain data from the Internet datacenter 209. In one embodiment,the Internet datacenter 209 comprises datacenter 208. The Internetdatacenter may optionally comprise at least one of a public andprivately owned datacenter.

In another embodiment, the upper tier Radiolet™ 233 replicates at leasta portion of the data extracted from the Internet datacenter 209 andtransmits the replicated data to another or a plurality of upper tierRadiolet(s)™ (not shown). Notably, the upper tier Radiolet™ 233 may belocated across a plurality of locations. The upper tier Radiolet™ 233and the other upper tier Radiolet™ (not shown) may be in communicationwith each other via at least one of a wired and wireless communicationslink.

In another embodiment, one or more over the top proxy Radiolets™ (notshown), positioned between the Internet datacenter 209 and the uppertier Radiolet™ 233, may be configured to extract the data extracted fromthe Internet datacenter 209 and distribute the data extracted from theInternet datacenter 209 to the upper tier Radiolet™ 233. These over thetop proxy Radiolet(s)™ (not shown) may each comprise at least oneprocessor executing computer-readable instructions to perform itsvarious functions.

The upper tier Radiolet™ 233 may further be configured to distribute atleast a portion of the received data to one or more lower tierRadiolets™ 231 upon request from the lower Radiolet(s)™ or pusheddirectly without request based on configured policies. Although thisexemplary network depicts a single lower tier Radiolet™ 231, it shouldbe understood that a system according to the present disclosure mayinclude any number of lower tier Radiolets™ in a given region.

As shown in this exemplary network 200, the lower tier Radiolet™ 231 maybe located closer to the source of the data request (e.g., BSC/PCF sever201) than the Internet datacenter 209. Notably, “closer to the source”may be measured in terms of network distance rather than physicaldistance. In an embodiment, the lower tier Radiolet™ 231 may be locatedat or proximal to a local switching site of a mobile data network 200.In another embodiment, the lower tier Radiolet™ 231 may be locatedbetween the BSC/PCF server 201 and the PDSN server 206 of the mobiledata network 200 of an HRPD standards based mobile data network. In yetanother embodiment, the lower tier Radiolet™ 231 may be located at everyBSC/PCF server 201 of a mobile data network 200. In yet anotherembodiment, the lower tier Radiolet™ is placed between the cell site andthe local switching office at a natural aggregation site.

The lower tier Radiolet™ 231 is shown in communication with the uppertier Radiolet™ 233 via at least one router/switch 215 over a managednetwork 224 (or any other wired or wireless communications link). Theupper tier Radiolet™ 233 may be configured to select the data that isdistributed to the lower tier Radiolet™ 231 based on one or more of: afrequency of requests for a particular type of data, one or morenetworking policies, one or more datacenter policies and one or morebusiness policies. Alternatively (or additionally), the lower tierRadiolet™ 231 may be configured to fetch data from the upper tierRadiolet™ 233. The lower tier Radiolet™ 231 may also be configured tostore portions of any received (or fetched) data, as well as perform oneor more of the following functions: processing dynamic content data,including (without limitation) manipulating inputted data to produceoutput data, content caching and storing data. To do this, the lowertier Radiolet™ 231 may comprise at least one processor executingcomputer readable instructions to perform its various functions.

In operation, the lower tier Radiolet™ 231 may receive a data requestfrom, for example, the BSC/PCF server 201 via the L2/L3/PBR switch orrouter 214 and the L2/L3/PBR switch or router 211. In an embodiment, thedata request may be received at the lower tier Radiolet™ 231 that islocated closest to the source of said data request. In anotherembodiment, the lower tier Radiolet™ 231 may be located at a localswitching site that receives the data request prior to transmitting thedata request to said lower tier Radiolet™ 231.

The lower tier Radiolet™ 231 may transmit, in response to said datarequest, data from the portion of received data to a source of the datarequest. The lower tier Radiolet™ 231 may establish a flow controlprotocol session between the lower tier Radiolet™ 231 and the source ofthe data request. The lower tier Radiolet™ 231 may then transmit thetraffic data to the source of the data request as a flow controlprotocol datagram.

In another embodiment, one or more operator proxy Radiolets™ 232 mayreceive data and information extracted from at least one server, forexample the AAA server 202, the policy server 203, and/or the prepaidserver 204 of a core network of the mobile data network 200 viaL2/L3/PBR switch/router 212 and managed IP network 223. Although thisexemplary network 200 depicts a single operator proxy Radiolet™ 232, itshould be understood that a system according to the present disclosuremay include any number of operator proxy Radiolets™.

The operator proxy Radiolet™ 232 may transmit at least a portion of theextracted information to the lower tier Radiolet™ 231, via a router 215over a managed network 224 (or any other wired or wirelesscommunications link). The extracted information may comprise informationfrom an authentication, authorization and accounting (e.g., AAA) server,information from a policy and charging rules function (e.g., PCRF)server, information from a real time mediation device (e.g., RTMD)server and/or information and data from any other type of server orsource. In this way, the operator proxy Radiolet™ 232 can support andimplement various fee-charging and policing interfaces (or any otherpolicy, security, management, business, etc. interfaces) as part of themobile communications network 200.

In an embodiment, the AAA server 202 may communicate with the PDSNserver 206 using a networking protocol, such as Remote AuthenticationDial In User Service (RADIUS), for example, to provide subscriberauthentication information to the PDSN server 206 during a subscribersession. The RADIUS protocol can be a networking protocol that providesauthentication, authorization and accounting management for subscribers.The operator proxy Radiolet™ 232 may request and receive a portion ofthe information from the AAA server 202 via a router or switch 212 and amanaged IP network 223. The operator proxy Radiolet™ 232 provides theinformation (e.g., subscriber information and session accountinginformation) from the AAA server 202 to the lower tier Radiolet™ 231 viarouter 215 and managed network 224.

In another embodiment, the policy server 203 may optionally be a PCRFserver. In operation, the operator proxy Radiolet™ 232 communicates andinterfaces with the PCRF server using Gx protocols, for example, whereGx is an online policy interface between the PDSN and the PCRF, viarouter or switch 212 and a managed IP network 223. The operator proxyRadiolet™ 232 provides information from the PCRF server to the lowertier Radiolet™ 231, via router 215 and managed network 224, that may beused to control policy functions (e.g., credit control request updateand credit control request termination).

The prepaid server 204 may optionally comprise a RTMD server. Theoperator proxy Radiolet™ 232 optionally communicates and interfaces withthe RTMD server using Diameter Gy protocols (e.g., DiameterCredit-Control (DCCA) protocol), for example, where Gy is an onlinecharging interface between the PDSN 206 and the RTMD servers, via routeror switch 212 and a managed IP network 223. The operator proxy Radiolet™232 provides information from the RTMD to the lower tier Radiolet™ 231,via for example router 215 and managed network 224, that may be used totag subscriber sessions as “prepaid” based on profile information of thesubscriber session.

In an embodiment, postpaid charging functions involve a RADIUS server(not shown) in communication with the lower tier Radiolet™ 231 via anoperator proxy Radiolet™ 232. In such an embodiment, the PDSN server 206collects radio specific parameters (e.g., Airlink Records) from a RadioAccess Network (RAN) and combines the radio specific parameters with IPnetwork specific parameters to form one or more Usage Data Records(UDR). The PDSN server 206 can use RADIUS protocols to send the UDRinformation to the RADIUS server. Each UDR data packet may be associatedwith a correlation ID, which identifies accounting records generated fora particular subscriber session and is provided to the RADIUS server bythe PDSN server 206 at the time authentication and authorization ofaccounting information is performed.

Similarly, in one embodiment, the operator proxy Radiolet™ 232 maycollect radio specific parameters from the RAN and combine the radiospecific parameters with IP network specific parameters to form UDR, anduse RADIUS protocols to send the UDR information to the RADIUS server(not shown). Optionally, the operator proxy Radiolet™ 232 may maintainthe UDR information until it receives confirmation that the RADIUSserver has properly received the information. If no confirmation isreceived from the RADIUS server within a period of time, the operatorproxy Radiolet™ 232 may retransmit the UDR information to the RADIUSserver. The operator proxy Radiolet™ 232 may transmit the UDRinformation to other RADIUS servers.

In one embodiment, various events that trigger the PDSN server 206 totake accounting action and send the UDR information may include (withoutlimitation) traffic data (e.g., A10 messages) connection termination atthe PDSN server 206, data service establishment, PPP renegotiations onthe PDSN server 206, arrival of subscriber data, and timer expiration.Various events that cause the PDSN server 206 to stop sending UDRinformation may include (without limitation), an existing A10 connectionis closed, an IP flow is removed from the corresponding A10, and thePDSN server 206 determines the packet data session associated with theCorrelation ID has ended.

The operator proxy Radiolet™ 232 may not require an event to triggeraccounting action, but may require an event to trigger UDR terminationincluding (without limitation) subscriber session termination or IP flowtermination.

In another embodiment, the lower tier Radiolet™ 231 may receive data orinformation from a management system server 234 via at least onerouter/switch 215 over a managed network 224 (or any other wired orwireless communications link). One or more management system servers 234may monitor the upper tier Radiolet™ 233 and lower tier Radiolet™ 231(e.g., monitoring the number of active IP tunneled sessions, thebandwidth usage of the subscriber sessions, the nature of the datarequests, and the frequency of network usage).

Turning now to FIG. 3, an exemplary network signaling data flow pathway321 and a traffic data flow pathway 322 according to an exemplaryembodiment of the present disclosure is shown.

The exemplary network signaling data flow pathway 321 comprises thecarrying of network signaling data, for example A11 messages in an HRPDstandards based mobile data network, from a subscriber mobile device 301to a central switching office 305, where the data is received at a cellsite 302, then sent to a local switching office 303, then to a regionalswitching office 304, and then to a central switching office 305 beforebeing routed to an Internet datacenter (e.g., 208 in FIG. 2) via theInternet point of presence (PoP)/Peering location 306 or the Internetconnection 307 (or any other wired or wireless communications link). Theregional switching office 304 and central switching office 305 may notbe local to the area where the mobile device 301 is located, and thenetwork signaling data served can traverse several hundreds of milesbefore reaching the mobile device 301.

The traffic data flow pathway 322, according to an exemplary embodimentof the present disclosure, involves the lower tier Radiolet™ 311receiving a data request at a local switching site 303, for example at aBSC/PCF (e.g., 201 in FIG. 2), from at least one subscriber mobiledevice 301. The data request is sent from the mobile device 301 to acell site 302 and then is sent from the cell site 302 to the localswitching site 303. The data request is routed from the local switchingsite 303 to the lower tier Radiolet™ 311.

The routing of the data request, according to an exemplary embodiment ofthe present disclosure, from the local switching site 303 to the lowertier Radiolet™ 311 comprises: a router(s) and a switch(es) (not shown)that identifies traffic data 322 and network signaling data 321; therouter or switch separates the traffic data 322, for example A10messages, from the network signaling data 321, for example A11 messages;the router or switch provides the network signaling data 321 to a corenetwork of a mobile data network; and the router or switch provides thetraffic data 322 to the at least one lower tier Radiolet™ 311. Thetraffic data 322 is then sent between the lower tier Radiolet™ 311, theupper tier Radiolet™ 312, and the Internet datacenter (e.g., 209 in FIG.2), bypassing the regional switching office 304 and the centralswitching office 306.

In an embodiment, the BSC/PCF server (e.g., 201 in FIG. 2) may beassociated with a PDSN server (e.g., 206 in FIG. 2) of a mobile datanetwork (e.g. 200 in FIG. 2). The IP addresses of the BSC/PCF server(e.g., 201 in FIG. 2) and the associated PDSN server (e.g., 206 in FIG.2) may be determined by a router or switch (e.g., L3 router/switch 214in FIG. 2) in order to separate the traffic data 322 from the networksignaling data 321. The traffic data 322 between the BSC/PCF server(e.g., 201 in FIG. 2) and the PDSN server (e.g., 206 in FIG. 2) may beidentified by a Generic Routing Encapsulation (GRE) protocol, forexample, using an IP protocol (e.g., IP-protocol type 47). Also, anydata packets that are not network signaling data 321 (e.g., not A11messages) may be identified as traffic data 322. The traffic data 322 isrouted by the router or switch (e.g., L3 router/switch 211 and 214 inFIG. 2) from the BSC/PCF server (e.g., 201 in FIG. 2) to the lower tierRadiolet™ 311. Traffic data 322 may also be routed via the router orswitch (e.g., L3 router/switch 211 and 212) and managed IP network(e.g., 224 in FIG. 2) to the PDSN server (e.g., 206 in FIG. 2). In anembodiment, the lower tier Radiolet™ 311 may be configured to interceptdomain name system (DNS) query packets from the BSC/PCF server (e.g.,201 in FIG. 2) and respond to the query to obtain the traffic data 322.In order for the traffic data 322 to maintain its properties, the lowertier Radiolet™ 311 may utilize an appropriate GRE key and BSC/PCF andPDSN IP addresses. The GRE key is used to create a traffic datatunneling connection between the lower tier Radiolet™ 311 and BSC/PCFserver (e.g., 201 in FIG. 2) and the traffic data 322 is routed from thelower tier Radiolet™ 311 to the BSC/PCF server (e.g., 201 in FIG. 2) andultimately to the subscriber mobile device 301. In an embodiment, asingle traffic data connection is implemented per subscriber wheremultiple IP flows are implemented into the one traffic data connection.The traffic data 322 may be packed into a Point-to-Point Protocol (PPP)stream. Since the PPP stream may require an in-sequence delivery oftraffic packets, the lower tier Radiolet™ 311 may sync its traffic datasequencing with the traffic data sequencing from the BSC/PCF server(e.g., 201 in FIG. 2) and PDSN server (e.g., 206 in FIG. 2).

The network signaling data 321 is then routed by a router or switch(e.g., L3 router/switch 211 and 212) between the BSC/PCF (e.g., 201 inFIG. 2) and the associated PDSN (e.g., 206 in FIG. 2), withoutmodification. In one embodiment, the network signaling data 321 may beexamined, for example, to identify relevant data or informationcontained in the network signaling data 321. The network signaling data321 may be routed via a router or switch (e.g., L3 router/switch 211 and214) to the lower tier Radiolet™ 311 for examination by the lower tierRadiolet™ 311, and then routed to the BSC/PCF server (e.g., 201 in FIG.2) or PDSN (e.g., 206 in FIG. 2) server. The lower tier Radiolet™ 311may obtain the GRE key and traffic data sequencing for the traffic data322 connection through examination of the network signaling data 321.

In another exemplary embodiment according to the present disclosure, amethod for data packet flow may provide for subscriber access to afictitious Internet site (e.g., www.xyz.com). According to this example,a subscriber may power up a mobile device which in turn discovers amobile communications network using methods known, or later known, inthe art, including (without limitation) probes, pilots, and control datathat is transmitted by the mobile device. The control data may be sentby the mobile device as long as the Internet site is still beingdownloaded, or if the mobile device is in the middle of an activesession. The mobile device may receive discovery messages from themobile communications network and register at the link layer usingmethods known, or later known, in the art. The mobile device may thenregister with a core network of the mobile communications network whichenables the mobile device to authenticate with the network, obtainnetwork addresses (both visited IP and home IP addresses), and establisha mobile session.

Next, the mobile device may send a domain name system (DNS) request forwww.xyz.com. This request packet may be identified by software of alower tier Radiolet™ and directed to an appropriate hosting Radiolet™(or virtual Radiolet™) at the lower tier Radiolet™ that is close(geographically) to the subscriber. The appropriate lower tier Radiolet™(or virtual Radiolet™) may resolve the domain name and translate it to alocal IP address on a lower tier Radiolet™ (or virtual Radiolet™) hostedat (or near) the same location. This resolved packet may then be sentback to the subscriber mobile device. The mobile device may then send arequest for a specific piece of content on the website using anHypertext Transfer Protocol (HTTP) get request packet, with the sourceIP address as itself and the destination IP address equal to theresolved IP address of the host server (obtained by sending the resolvedpacket back to the subscriber mobile device). The lower tier Radiolet™(or virtual Radiolet™) may then establish a TCP session and start todeliver content to the mobile device, where the flow control algorithmand parameters may be modified and adapted based on previous history ofbandwidth estimates between the server and mobile device. Such historyinformation may be shared across servers (and virtual servers) that arehoused in the same location. After all requested data packets aredelivered, the HTTP session may be terminated.

In one embodiment of this disclosure, the content delivered to themobile device is readily available at the hosting location (e.g., at thelower tier Radiolet™). If the content is not readily available at thelower tier Radiolet™, then the upper tier Radiolet™ may fetch contentthrough a back-to-back (B2B) User Agent from the internet datacenter.The B2B User Agent may serve as a client to the internet datacenter andas a server to the mobile device.

The details of the number of data bytes and related information may thenbe reported by the lower tier Radiolet™ to both operator network billingsystems and cloud datacenter metering systems.

In the above exemplary embodiment, the appropriate hosting lower tierRadiolet™ may be located very close to the subscriber, and before thestart of the Mobile Middle Mile™. This allows for the round trip time(RTT) to be reduced thereby leading to reduction in mobile latency. Byreducing the mobile latency, the amount of control data sent by themobile device during the download is also reduced. Also, once thedelivery of the webpage is complete, more webpages for the samesubscriber mobile device or new webpages for a different subscribermobile device can begin to be delivered, which can allow for improvementin radio efficiency.

Additionally, in the above exemplary embodiment, the appropriate networkawareness to the application and application awareness to the networkmay be created using at least one network API and/or at leastapplication API, thereby improving subscriber QoE.

Furthermore, optimizations may be added to flow control, providing forfurther reduction in mobile latency along with simultaneous improvementsin radio efficiency. Also, given that traffic data does not traverse theMobile Middle Mile™, the amount of traffic data handled by the corenetwork of a mobile communications network is reduced, which can lead tocorresponding improvements in efficiencies. Finally, neither theoperator network nor the cloud datacenter need to be upgraded.

In yet another exemplary embodiment, a method of reducing a round triptime (RTT) for traffic packets is provided. The method provides contentto a content requestor, where the content can be one or more of staticcontent, dynamic content, a real-time or delayed media feed, applicationdata, or any other type of content, and can be in the form of trafficdata packets. The method provides for a reduction of an end-to-endlatency of a session, where the session can one or more of a webpage, adata stream and an application.

The method includes identifying, by a processor executingcomputer-readable instructions, a location of a data requestor where therequestor requests traffic data packets. The requestor can be asubscriber or subscriber mobile device of a mobile data network. Then,identifying, by a processor executing computer readable instructions, acontent distribution entity configured to provide the requested trafficpackets. The content distribution entity can be a Radiolet™ and can belocated proximate to a location of the data requestor. Notably,“proximate” may optionally refer to a measure of network distance ratherthan physical distance. A processor executing computer readableinstructions can then transmit the requested traffic packets to therequestor from the proximate content distribution entity.

The method may also include pushing content and application data fromone or more content providers to the content distribution entity in realtime and storing the content at the content distribution entity forcurrent and/or future requests. The distribution entity may optionallytransmit up-to-date traffic packets in response to traffic packetrequests.

Transmitting the requested content and application data packets from theproximate content or application data distribution entity can reduce asession time and can simultaneously reduce the load on a wirelesscommunication link by reducing reverse link traffic attributed tocontrol layer messages. The method can further include servicingadditional traffic packets via the same shared wireless communicationlink.

In yet another exemplary embodiment, a method may improve mobile datanetwork efficiency and can improve the efficiency of an internetdatacenter by reducing the number of content and/or application sessionshosted in the datacenter.

The method includes separating, by a processor executingcomputer-readable instructions, signaling and management function datafrom traffic function data. The management function data may be providedby a management entity and the traffic function data may be provided bya traffic entity. The method may further include receiving, by aRadiolet™, one or more requests for traffic data; and identifying andseparating, by a processor executing computer readable instructions,traffic data packets from signaling data packets included in therequests for traffic data.

The method may also include identifying, by a processor executingcomputer-readable instructions, a location of a source of the requestsfor traffic data and a traffic entity closest to the source, andservicing the traffic packets from a proximate traffic entity or theclosest traffic entity. Servicing traffic packets from the proximatetraffic entity or the closest traffic entity may reduce a session timeand reduce the load on a wireless communication link or datacenter byreducing reverse link traffic attributed to control layer messages.Notably, “proximate” may refer to a measure of network distance ratherthan physical distance. The method may also include servicing additionaltraffic packets via the same shared wireless communication link.

The method may further include servicing the signaling data packets viathe existing packet core network entity and applying various methodsrelated to flow control and resource management in the traffic plane.Appropriate parameters may be chosen as input to the flow control andresource management methods.

In still another exemplary embodiment, a method may provide for mobilelatency reduction and more generally improvement in applicationperformance. The method includes transmitting data content from Internetsites or enterprises to upper tier Radiolets™ located at upper tierRadiolet™ locations and replicating, transmitting and storing the datacontent at additional upper tier Radiolets™ located at additional uppertier Radiolet™ locations. Determining which additional upper tierRadiolet™ locations receive the replicated data content may be based ona combination of predetermined static and dynamic rules. The method mayalso include replicating and transmitting the data content directly tolower tier Radiolets™ from the upper tier Radiolets™.

The method includes delivering content or application data, in responseto requests for traffic data from a requestor, to the lower tierRadiolet™ closest to the requestor. The delivering content orapplication data step may include identifying, by a processor executingcomputer-readable instructions, a location of the requestor, identifyingand separating traffic packets from signaling packets included in therequests for traffic data, transmitting all signaling traffic packets toa network entity and transmitting all traffic packets to the lower tierRadiolet™ closest to the requestor. The lower tier Radiolet™ may thentransmit requested traffic data to the requestor.

In yet another exemplary embodiment, a method includes receiving, by aRadiolet™, one or more requests for traffic data and separating, by aprocessor executing computer-readable instructions, signaling andmanagement functions from traffic functions such that the signaling andmanagement functions are provided by a management entity and the trafficfunctions are provided by a traffic entity. The traffic entity maycomprise a content distribution entity.

The method includes identifying and separating, by a processor executingcomputer-readable instructions, traffic packets from signaling packetsincluded in the one or more requests for traffic data and identifying acontent distribution entity configured to provide the requested trafficdata. The content distribution entity may be located proximate to thedetermined location of the requestor.

The method may further include servicing the signaling packets via theexisting packet core network entity, transmitting the requested trafficdata to the requestor from the proximate content distribution entity,and applying various methods related to flow control and resourcemanagement.

In a further exemplary embodiment, any of the features and/or methodsteps described herein may be embodied in and/or implemented by any ofthe systems, devices, processors or apparatus described herein.Moreover, any of the method steps described herein may be implemented inan operator network and/or an Internet cloud datacenter using existingequipment and apparatus by implementing one or more softwareapplications having computer readable instructions that when executedcause said existing equipment and apparatus to perform (or exhibit) oneor more of the method steps and/or features described in thisdisclosure.

A system according to the present disclosure may comprise one or morecomputer devices comprising one or more processors configured to executecomputer readable instructions that, when executed, cause said one ormore computer devices to perform any of the method steps (and/or exhibitany of the features) described herein. The computing devices may includeany combination of (and any number of) Radiolets™, datacenters,computers, data sources, data request sources, servers, mobilecommunication devices, smart phones, tablets, any other mobiletelecommunication and/or mobile data network elements, and/or any othercomputing and/or communication devices.

Notably, the systems and methods described herein are not limited totypical mobile communications. Instead, the systems and methodsdescribed herein may be in connection with mobile entertainmentenablement solutions, mobile infotainment enablement solutions, mobilead-tech enablement solutions, mobile social media enablement solutions,mobile commerce enablement solutions, mobile enterprise applicationenablement solutions, mobile peer-to-peer enablement solutions, mobilecommunications enablement solutions mobile enterprise applicationenablement solutions, and other mobile solutions such as toll-free dataenablement solutions.

While the present disclosure has been discussed in terms of certainembodiments, it should be appreciated that the present disclosure is notso limited. The embodiments are explained herein by way of example, andthere are numerous modifications, variations and other embodiments thatmay be employed that would still be within the scope of the presentdisclosure.

1. A system of delivering data, the system comprising: at least oneupper tier radiolet comprising at least one processor executingcomputer-readable instructions that cause the at least one upper tierradiolet to: receive data extracted from an Internet datacenter, anddistribute at least a portion of the received data to at least one lowertier radiolet; and the at least one lower tier radiolet in communicationwith the at least one upper tier radiolet via at least one of a wiredand wireless communications link, the at least one lower tier radioletcomprising at least one processor executing computer-readableinstructions that cause the at least one lower tier radiolet to: storesaid portion of the received data, receive a data request, and transmit,in response to said data request, data from the portion of received datato a source of the data request, wherein the at least one lower tierradiolet is located closer to the source of the data request than theInternet datacenter.
 2. The system of claim 1, wherein the at least oneupper tier radiolet executes computer-readable instructions that causethe at least one upper tier radiolet to: replicate at least a portion ofthe data extracted from the Internet datacenter, and transmit saidreplicated data to at least one other upper tier radiolet.
 3. The systemof claim 2, wherein the upper tier radiolets are located across aplurality of locations.
 4. The system of claim 2, wherein the at leastone upper tier radiolet and the at least one other upper tier radioletare in communication with each other via at least one of a wired andwireless communications link.
 5. The system of claim 1, wherein the atleast one upper tier radiolet is located at or proximal to the Internetdatacenter and is in direct communication with said Internet datacentervia at least one of a wired and wireless communications link, saidInternet datacenter comprising at least one of a public and privatelyowned datacenter.
 6. The system of claim 1, further comprising: at leastone over the top proxy radiolet in communication with the at least oneupper tier radiolet via at least one of a wired and wireless network andpositioned between the Internet datacenter and the at least one uppertier radiolet, the at least one over the top proxy radiolet comprisingat least one processor executing computer-readable instructions thatcause the at least one over the top proxy radiolet to: extract the dataextracted from the Internet datacenter, and distribute the dataextracted from the Internet datacenter to the at least one upper tierradiolet.
 7. The system of claim 1, wherein the at least one lower tierradiolet executes computer-readable instructions that cause the at leastone lower tier radiolet to fetch at least a portion of the received datafrom the at least one upper tier radiolet.
 8. The system of claim 1,wherein the at least one lower tier radiolet is in communication withthe at least one upper tier radiolet via at least one of a router and aswitch.
 9. The system of claim 1, wherein the at least one upper tierradiolet executes computer-readable instructions that cause the at leastone upper tier radiolet to select the data distributed to the at leastone lower tier radiolet based on one or more of: a frequency of requestsfor a particular type of data, one or more networking policies, one ormore datacenter policies and one or more business policies.
 10. Thesystem of claim 1, wherein the at least one lower tier radiolet executescomputer-readable instructions that cause the at least one lower tierradiolet to perform one or more of the following functions: processingdynamic content data, content caching and storing data.
 11. The systemof claim 1, wherein the at least one lower tier radiolet is located ator proximal to a local switching site of a mobile data network.
 12. Thesystem of claim 11, wherein the mobile data network comprises a HighRate Packet Data (HRPD) network and wherein the at least one lower tierradiolet is located between a Packet Control Function (PCF) server and aPacket Data Service Node (PDSN) of the mobile data network.
 13. Thesystem of claim 11, wherein the mobile data network comprises a HighSpeed Packet Access (HSPA) network and wherein the at least one lowertier radiolet is located between a Radio Network Controller (RNC) serverand a Gateway GPRS Support Node (GGSN) of the mobile data network. 14.The system of claim 11, wherein the mobile data network comprises aLong-Term Evolution (LTE) network and wherein the at least one lowertier radiolet is located between a S1 Concentrator and a Packet DataGateway (PGW) of the mobile data network.
 15. The system of claim 11,further comprising: at least one operator proxy radiolet incommunication with the at least one lower tier radiolet via at least oneof a wired and wireless network, the at least one operator proxyradiolet comprising at least one processor executing computer-readableinstructions that cause the at least one operator proxy radiolet to:receive information extracted from at least one server of a core networkof the mobile data network, and transmit at least a portion of theextracted information to the at least one lower tier radiolet prior totransmitting data to the source of the data request.
 16. A method ofdelivering data, the method comprising: receiving, by at least one uppertier radiolet comprising at least one processor executingcomputer-readable instructions, data extracted from an Internetdatacenter; distributing, by the at least one upper tier radiolet, atleast a portion of the received data to at least one lower tierradiolet, said at least one lower tier radiolet comprising at least oneprocessor executing computer readable instructions; storing, by the atleast one lower tier radiolet, said portion of the received data;receiving, by the at least one lower tier radiolet, a data request; andtransmitting, by the at least one lower tier radiolet and in response tosaid data request, data from the portion of received data to a source ofthe data request, wherein the at least one lower tier radiolet islocated closer to the source of the data request than the Internetdatacenter.
 17. The method of claim 16, further comprising: replicating,by the at least one upper tier radiolet, at least a portion of the dataextracted from the Internet datacenter; and transmitting, by said atleast one upper tier radiolet, said replicated data to at least oneother upper tier radiolet.
 18. The method of claim 17, wherein the uppertier radiolets are located across a plurality of locations.
 19. Themethod of claim 17, wherein the at least one upper tier radiolet and theat least one other upper tier radiolet are in communication with eachother via at least one of a wired and wireless communications link. 20.The method of claim 16, wherein the at least one upper tier radiolet islocated at or proximal to the Internet datacenter and is in directcommunication with said Internet datacenter via at least one of a wiredand wireless communications link, said Internet datacenter comprising atleast one of a public and privately owned datacenter.